What about upper limit to fatigue/cooldown to something like 30min ?

and why 5 LY ?

ccp,

can you explain the reasoning behind not putting the limits/nerfs on the cyno itself...vs on every capital?
...

You're misunderstanding. What I'm saying is with the cool down timer for moving toons through a Titan's Jump Portal, alliances with a small number will be impacted for more than alliances with a larger number. While 1 Titan is cooling down, a larger alliance will just use another. Small groups don't have that option.

This will alienate a lot of elite pvp'ers and veterans from the game.

Congrats to CFC for winning the game.
Blue donut FTW!
After this batphones won't work and only the largest entities can muster large cap and supercap entities as others can't concentrate forces.

CCP you do know that this will only hurt small groups as much if not more then large ones right?

The only people these changes will hurt are those who have nothing to do with SuperCap fleet actions in the first place

Grayscale, are you sure it's a good idea to have an exponentially increasing fatigue timer with only a linear decrease?

If I do 16 jumps I will have a 2.7 million years of fatigue, is that correct?

The fatigue timer should be capped at 15 minutes. It should not increase beyond that. This would be sufficient to prevent people crossing the map and you wouldn't have any "ruined" characters with multiple years of fatigue.

I'm already EFTing a Nano-Nid!!!!!

Enjoying trying to get that moon goo to market, through lowsec. Paying everyone in your convoy ops is going to eat into those tasty profits.

So CCP saw it fit to kill off Blops...

...but afk cloaky camping remains perfectly viable.

Good job, CCP, good job..

Blops can be avoided and countered: be alert, stay aligned et cetera. There's no viable counter measure against cloaky camping. Please explain why killing off blops is a good thing, instead of killing off cloaky camping?

Almost 100 pages of tears. Look at all those buckets. :D

I dunno, I rather enjoy it

Please. The gate feature is absurd. No one is going to move capitals through gates as part of a strategy. They may tactically do it if they have full confidence on the space being safe, but no one will devise a strategy that ever includes a capital fleet gate jump. It's too hard to keep gates secure for the flight times and align times of capitals and the value/risk ratio on a 4B per ship fleet of mega slow ships just doesn't make sense.

Counter proposal for the jump delay timer.

Link below is a google excel doc. of cumulative delay timer that incrementally gets longer with each jump.

http://bit.ly/1rOpzTs

ItGÇÖs a logarithmic scale.

So when you jump you get two timers.

First timer is the jump drive timer; the second timer is jump drive activation delay.

The jump drive timer is a base 30 minutes and every time you make a jump it will record the amount and add +1 to the "Jumps Made Since Timer Began" value. The jump drive timer will reset back to 30 min every time you make a new jump.
The jump drive activation delay is the timer you get once you have jumped. ItGÇÖs the time you have to wait till the next jump can be made.

The equation for this is below.

http://i.imgur.com/EQpv4Cv.png

The principal of what happens here is that your delay timer gets bigger with each jump. The increment between each subsequent timer gets smaller, causing the graph to plateau out into a logarithmic curve. Eventually after so many jumps the delay timer will reach the same value as the jump drive timer, at which point itGÇÖs better with it out entirely and then start the process over.

Initially we found a problem with the function where doing three really short distance jumps would make the times later overall shorter but that has been fixed with the GÇ£Jump Amount Modifier.GÇ¥

So e.g.
Jump 1 > 4.19 LY > delay timer of 6.42min > cumulative time 6.42min
Jump 2 > 4.7 LY > delay timer of 9.72 min > cumulative time 16.14min
Jump 3 > 4.206 LY > delay timer of 11.73 min > cumulative time 27.86min
Jump 5 > 4.564 LY > delay timer of 13.28 min > cumulative time 41.14min
Jump 6 > 1.855 LY > delay timer of 14.15 min > cumulative time 55.29min

Notice the increase in time getting smaller but the time overall still get longer. Bit like the diminishing returns of stacking nerf.

This Post and Equation was worked on by Sieonigh and myself.

Edit: We made this formula under the assumption that Jump Freighters and Rorquals do NOT have the 90% reduction, rather we think Black Ops should have this reduction (which we're implementing).

This also reduces the insanely long multi-year trips, making them instead, multi-month trips,

dude are you stupid? 1 or 2 hics you say? how can 2 hics hold 4-5 -9 caps in place till the rest of your gang wait the agro and jump? are those hics using capital sized reps now or what?

Do you really want to kill deep 0.0? How can a small alliance live in deep space, if they are not able to control the whole way from and to there area?

On a less serious note when can we expect ECM to be buffed, because it is seriously underpowered when there's a chance single targets can get lock against 5 EC-300's.

The eve universe is crowded, add another dimension, perhaps only accessible by wh's or something

How dank does one have to be to join goons anyway? :D I might be looking for a new corp

This change is probably a buff to defenders.

Get it?

Mostly here to get in on a 300+ page thread. oh and I think these changes are going to be great for the game!

I dunno if anyone has actually calculated it out, but even with infinitely capable servers the speed of light limit might actually even put getting rid of TiDi as complete impossibility so long as all players are not in the same room with the servers.

As a player who lives in null sec and relies on jump bridges to get around this is a terrible change.

I've been playing since beta and this by far is the worst thing you've done to your game since... well ever...

Seems CCP stopped reading this at page 200 so this seems to be just a debate between ourselves at this point.

Maybe time to lock the thread if CCP have stopped reading the feedback they asked for !

Not speed of LIGHT, but the SPEED at which light propagates. All electronics and cables deal with pulse wave propagation issues, the pulses traveling through conductors at near the speed of light. Of course optical fiber cables do transactions over light, so it is apples to apples there. :)

He's actually not completely wrong.

Whats next CCP? Capital ships in hi sec?

Because imagine marmites or other high sec mercs with nuetral triage plus refits if they know their shiny is going to die